Customizing Data Transport Service › Creating a Network Topology

Creating a Network Topology

The framework for a Data Transport Service network is created when the Install Network Business Process Views and Data Transport Auto Discovery processes are performed. It includes three Business Process Views: DTS Managers Configuration, DTS Agents Configuration, and DTS Administration. The Data Transport objects—DTS managers and DTS agents—are visually depicted in these views and become eligible for object management through the WorldView 2D Map and 3D Map.

You can define the machines in your network, the network topology among the machines in this network, and the communication routes to follow when transferring data between its machines. Establishing a network topology for your Data Transport Network lets you define a strict hierarchical network structure, by which the Data Transport Service determines the routes to use for transfers between the machines of your network.

Defined machine and network properties, which are set using the DTS Administration Client interface and stored in the MDB, are responsible for establishing the hierarchical and network-related relationships between the machines of your network. These relationships enforce the route used to complete transfers through and between the machines of your network.

Machine and network properties can be set at the machine, interface, machine container, and link levels. If multiple sets of properties are encountered when attempting to resolve a route through the network, then the transfer property precedence is followed to determine the machine and network properties having the most influence over the transfer. Once determined, the transfer inherits these property values and the route is resolved.

Machines included in your network topology that are not defined in a hierarchy comprised of one or a number of links are assumed to have point-to-point connectivity to all other machines in your network.

Consider the following domain network topology:

This example defines a network topology among the machines of a Client Automation domain. Hierarchies of machines, together with machines that are not a part of any defined hierarchy, exist in the same network topology.

When considering the relationships established among the machines due to the defined network topology, you can conclude the following:

• Machines A, B and the machines of the Machine Container (C, D and E) comprise a hierarchy.
• Machines F, G and H and machines I, J and K are also examples of separate established hierarchies.
• Machines C, D and E are members of a Machine Container; you can define common transfer properties for these machines once at the container level, yet apply them to all the machines of the container. Defined Machine Container properties take precedence over the individual machine properties.
• No defined routes exist between Machines C, D and E; similarly, no defined route exists between Machines B and G. When you initiate a transfer between these machines, point-to-point, TCP/IP connectivity is assumed.
• A route from Machine A to Machine E is resolved into two routes: one from Machine A to Machine B and a second from Machine B to Machine E.

Note: For more information, see the CA WorldView documentation for Business Process Views.